Configuring the layout of a keyboard using gestures

ABSTRACT

Systems and methods for configuring the layout of a hovering keyboard using gestures are described. In some embodiments, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to: detect a hand gesture using proximity sensors disposed on a hovering keyboard coupled to the IHS, and configure a layout of the hovering keyboard based on the detection.

FIELD

This disclosure relates generally to Information Handling Systems(IHSs), and more specifically, to systems and methods for configuringthe layout of a hovering keyboard using gestures.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is Information Handling Systems (IHSs). AnIHS generally processes, compiles, stores, and/or communicatesinformation or data for business, personal, or other purposes therebyallowing users to take advantage of the value of the information.Because technology and information handling needs and requirements varybetween different users or applications, IHSs may also vary regardingwhat information is handled, how the information is handled, how muchinformation is processed, stored, or communicated, and how quickly andefficiently the information may be processed, stored, or communicated.The variations in IHSs allow for IHSs to be general or configured for aspecific user or specific use such as financial transaction processing,airline reservations, enterprise data storage, or global communications.In addition, IHSs may include a variety of hardware and softwarecomponents that may be configured to process, store, and communicateinformation and may include one or more computer systems, data storagesystems, and networking systems.

In various implementations, IHSs process information received via akeyboard. A conventional keyboard includes components such as scissorswitch keys, dome switch keys, levers, membranes, bucking springs, etc.These components are configured to receive physical keystrokes when auser actually touches and/or presses the keyboard's keys.

In addition, certain types of keyboards now also come equipped withproximity sensors. These proximity sensors are configured to measuredistances between the user's hand or fingers to the keyboard. Inoperation, such a keyboard can detect signals representative ofproximity and, when appropriate, it can interpret them as “hoveringkeystrokes”—even in the absence of physical contact between the keyboardand the user's fingers.

SUMMARY

Embodiments of systems and methods for configuring the layout of ahovering keyboard using gestures are described. In an illustrative,non-limiting embodiment, an Information Handling System (IHS) mayinclude a processor and a memory coupled to the processor, the memoryhaving program instructions stored thereon that, upon execution by theprocessor, cause the IHS to: detect a hand gesture using proximitysensors disposed on a hovering keyboard coupled to the IHS, andconfigure a layout of the hovering keyboard based on the detection.

To detect the hand gesture, the program instructions, upon execution,may the IHS to fit proximity data obtained by the proximity sensors to ageometric model of a hand. In some cases, the geometric model mayinclude a partial virtual skeleton of the hand having one or moreparameters selected from the group consisting of: a length, a width, ajoint position, an angle of joint rotation, and a finger segment.

For example, the hand gesture may include a swipe. To configure thelayout, the program instructions, upon execution, further cause the IHSto map a key selected by a user to a corresponding command.

To configure the layout, the program instructions, upon execution, maycause the IHS to detect hovering keystrokes to the exclusion of physicalkeystrokes. Additionally, or alternatively, to configure the layout, theprogram instructions, upon execution, further cause the IHS to detectphysical keystrokes to the exclusion of hovering keystrokes.Additionally, or alternatively, to configure the layout, the programinstructions, upon execution, further cause the IHS to detect physicalkeystrokes and hovering keystrokes concurrently. Additionally, oralternatively, to configure the layout, the program instructions, uponexecution, further cause the IHS to map a first hovering keystroke overa first keycap to a first application executed by the IHS, and to map asecond hovering keystroke over a second keycap to a second applicationexecuted by the IHS.

In some cases, the first application may be rendered on a displayintegrated into the IHS, and wherein the second application may berendered on an external display.

To configure the layout, the program instructions, upon execution, maycause the IHS to map a hovering keystroke over a given keycap to a firstapplication executed by the IHS, and to map a physical keystroke of thegiven keycap to a second application executed by the IHS. Additionally,or alternatively, to configure the layout, the program instructions,upon execution, cause the IHS to enable hovering keystrokes over a firsta subset of keycaps and disable hovering keystrokes over a second subsetof keycaps. Additionally, or alternatively, to configure the layout, theprogram instructions, upon execution, may cause the IHS to enable ordisable a lighting effect provided via a backlight illumination layer ofthe hovering keyboard.

In another illustrative, non-limiting embodiment, a method may includedetecting a hand gesture using proximity sensors disposed on a hoveringkeyboard coupled to an IHS, and configuring a layout of the hoveringkeyboard based on the detection. For example, detecting the hand gesturemay include fitting proximity data obtained by the proximity sensors toa partial virtual skeleton of the hand having one or more parametersselected from the group consisting of: a length, a width, a jointposition, an angle of joint rotation, and a finger segment.

In some cases, configuring the layout may include configuring thehovering keyboard to detect one of: (i) hovering keystrokes only, (ii)physical keystrokes only, or (iii) physical keystrokes and hoveringkeystrokes concurrently. Additionally, or alternatively, configuring thelayout may include mapping a hovering keystroke over a given keycap to afirst application executed by the IHS and mapping a physical keystrokeof the given keycap to a second application executed by the IHS.Additionally, or alternatively, configuring the layout may includeenabling hovering keystrokes over a first a subset of keycaps anddisabling hovering keystrokes over a second subset of keycaps.Additionally, or alternatively, configuring the layout may includeselecting a color or an intensity of a light provided by a backlightillumination layer of the hovering keyboard.

In yet another illustrative, non-limiting embodiment, a hardware memorydevice may have program instructions stored thereon that, upon executionby a processor of an IHS, cause the IHS to: detect a hand gesture usingproximity sensors disposed on a hovering keyboard coupled to the IHS;and configure a layout of the hovering keyboard based on the detection.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention(s) is/are illustrated by way of example and is/arenot limited by the accompanying figures, in which like referencesindicate similar elements. Elements in the figures are illustrated forsimplicity and clarity and have not necessarily been drawn to scale.

FIG. 1 is a perspective view of an Information Handling System (IHS)with a hovering keyboard, according to some embodiments.

FIG. 2 is a block diagram of electronic components of an IHS, accordingto some embodiments.

FIG. 3 is a block diagram of electronic components of a hoveringkeyboard, according to some embodiments.

FIG. 4 is sectional view of a hovering keyboard in operation, accordingto some embodiments.

FIGS. 5A and 5B are diagrams of a hovering keyboard being used to detecthand gestures, according to some embodiments.

FIG. 6 is a flowchart of a method for configuring the layout of ahovering keyboard using gestures, according to some embodiments.

FIG. 7 is a diagram of different zones of a hovering keyboard, accordingto some embodiments.

FIG. 8 is a diagram of a configuration example, according to someembodiments.

DETAILED DESCRIPTION

For purposes of this disclosure, an IHS may include any instrumentalityor aggregate of instrumentalities operable to compute, calculate,determine, classify, process, transmit, receive, retrieve, originate,switch, store, display, communicate, manifest, detect, record,reproduce, handle, or utilize any form of information, intelligence, ordata for business, scientific, control, or other purposes. For example,an IHS may be a personal computer (e.g., desktop or laptop), tabletcomputer, mobile device (e.g., Personal Digital Assistant (PDA) or smartphone), server (e.g., blade server or rack server), a network storagedevice, or any other suitable device and may vary in size, shape,performance, functionality, and price. An IHS may include Random AccessMemory (RAM), one or more processing resources such as a CentralProcessing Unit (CPU) or hardware or software control logic, Read-OnlyMemory (ROM), and/or other types of nonvolatile memory. Additionalcomponents of an IHS may include one or more disk drives, one or morenetwork ports for communicating with external devices as well as variousI/O devices, such as a keyboard, a mouse, touchscreen, and/or a videodisplay. An IHS may also include one or more buses operable to transmitcommunications between the various hardware components.

FIG. 1 is a perspective view of Information Handling System (IHS) 100with hovering keyboard 103. In this illustrative, non-limitingembodiment, IHS 100 includes display 101 and base or chassis 102,coupled to each other via hinge 104. Chassis 102 includes trackpad 105or the like, and it holds keyboard 103. In this implementation, IHS 100has a laptop or notebook form factor, such that keyboard 103 is directlyintegrated thereto. In other implementations, however, IHS 100 may be adesktop computer, video game console, appliance, etc., and keyboard 103may be a peripheral keyboard separate from IHS 100. In those cases,keyboard 103 may be coupled to IHS 100 via a cable or wire (e.g., over aPS/2 connector, USB bus, etc.) or wirelessly (e.g., Bluetooth). Inputsmade at keyboard 103 are communicated to keyboard controller 300 (shownin FIG. 3) for use by IHS 100.

In this example, hovering keyboard 103 is depicted with three layers ormembranes: an electromechanical layer 103A, backlight illumination layer103B, and proximity sensing layer 103C. When hovering keyboard 103 isassembled, layers 103A-C are stacked on top of each other to operate asfollows: Electromechanical layer 103A is where keycap assemblies reside,and it is configured to detect physical keypresses against key caps;backlight illumination layer 103B comprises a plurality of LEDsconfigured to illuminate key caps from the bottom up; and proximitysensing layer is configured to detect hovering keypresses, such that insome cases, a finger's proximity to a key cap, without actually touchingit, can also be detected as a keypress.

In other hovering keyboard implementations, the order in which layers103B and 103C are stacked may be different than what is shown in FIG. 1.In some cases, layers 103A-C may be combined: for example, layers 103Band 103C may be provided as a single membrane.

With respect to electromechanical layer 103A, key caps extend out of anupper surface of keyboard 103 to provide a user with selectable inputsbased upon the characters associated with the keys, such as a QWERTYkeyboard that provides ASCI binary code inputs to the keyboardcontroller. A membrane disposed beneath keys may detect key inputs andgenerate a signal unique to each key. The membrane may be, for example,a flexible printed circuit board with wirelines that feed to a cable sothat key inputs may be uniquely identified. Lever structures may bedisposed below the keycaps to bias the keys in an upwards direction. Endusers provide inputs by pressing on keys to overcome the bias of theselever structures, to thereby impact the membrane.

As a person of ordinary skill in the art will recognize, hoveringkeyboard 103 may have a variety suitable of structures for placement ofkeys as individual caps (or assembled as one part) and for biasing keys(such as springs, magnets, and/or other types of devices).

Electromechanical layer 103A provides a grid of circuits underneath thekeys of keyboard 103 that forms an N×M matrix. These circuits areconfigured to generate signals in response to the user pressing thekeys. For example, the circuits may be broken underneath the keys suchthat, when a user depresses a given key, the electric circuit underneaththat key is completed. Keyboard controller 300 receives a signal outputby that circuit and compares the location of the circuit to a charactermap stored in its memory to determine which key was physically pressed.

Backlight illumination layer 103B may include an Organic Light EmittingDiode (OLED) material, such as an OLED film that is selectively poweredwith an electrical current under the control of keyboard controller 300.The OLED film be disposed at various locations of keyboard's structurein order to obtain desired illumination at selected keys. For example,the OLED film may be deposited directly on electrical contacts ofmembrane 103B so that a controller may selectively illuminate OLED filmunder any keycap, by applying an electrical current to it. In somecases, backlight illumination layer 103B may further include alightguide structure or the like, configured to route light from its LEDsource to a particular keycap through keyboard 103.

Proximity sensing layer 103C provides keyboard 103 with the ability todetect keypresses without the end user making physical contact with keycaps. The proximity sensors of sensing layer 103C may comprise any of anumber of different types of known sensors configured to measure adistance or proximity of an object, and to produce corresponding signalsin response. In some implementations, proximity sensors may overlay orlie underneath the keys of hovering keyboard 103. In otherimplementations, sensors may be integrated within each respective key.

In the embodiment of FIG. 1, the proximity sensors may include a grid ofsensors underneath the keys of keyboard 103 disposed on layer 103C. Theproximity sensors may be capacitive sensors configured such that theirelectric fields (sensing fields) are directed through the key caps andupward from the top surface keyboard 103. The proximity sensors areconfigured to detect an object such as a user's fingers, and to producesignals representative of the proximity of the object. Keyboardcontroller 300 may process these signals to determine the positionand/or movement of the detected object relative to the proximitysensors, and to capture inputs having certain characteristics ascorresponding hovering keystrokes.

In some implementations, the detection of hovering keystrokes viaproximity sensing layer 103C may take place in addition, or as analternative to, the concurrent detection of physical keystrokes byelectromechanical layer 103A.

FIG. 2 is a block diagram of components of IHS 100. Particularly, IHS100 may include one or more processors 201. In various embodiments, IHS100 may be a single-processor system including one processor 201, or amulti-processor system including two or more processors 201.Processor(s) 201 may include any processor capable of executing programinstructions, such as an INTEL PENTIUM series processor or anygeneral-purpose or embedded processors implementing any of a variety ofInstruction Set Architectures (ISAs), such as an x86 ISA or a ReducedInstruction Set Computer (RISC) ISA (e.g., POWERPC, ARM, SPARC, MIPS,etc.).

IHS 100 includes chipset 202 that may have one or more integratedcircuits coupled to processor(s) 201. In certain embodiments, thechipset 202 may utilize a DMI (Direct Media Interface) or QPI (QuickPathInterconnect) bus 203 for communicating with processor(s) 201.

Chipset 202 provides processor(s) 201 with access to a variety ofresources. For instance, chipset 202 provides access to system memory205 over memory bus 204. System memory 205 may be configured to storeprogram instructions and/or data accessible by processors(s) 201. Invarious embodiments, system memory 205 may be implemented using anysuitable memory technology, such as static RAM (SRAM), synchronousdynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type ofmemory.

Chipset 202 may also provide access to graphics processor 207. Incertain embodiments, graphics processor 207 may be part of one or morevideo or graphics cards that have been installed as components of IHS100. Graphics processor 207 may be coupled to chipset 202 via graphicsbus 206 such as provided by an Accelerated Graphics Port (AGP) bus, or aPeripheral Component Interconnect Express (PCIe) bus. In certainembodiments, graphics processor 207 generates display signals andprovides them to display device 208. In certain embodiments, displaydevice 208 may be a touch-sensitive display.

In some implementations, chipset 202 may also provide access to one ormore user input devices 211. For instance, chipset 202 may be coupled tosuper I/O controller (SIO) 210 or an embedded controller (EC) via eSPI(Enhanced Serial Peripheral Interface) or Low-Pin Count (LPC) bus 213,and SIO 210 may provide interfaces for a variety of user input devices211 (e.g., lower bandwidth and low data rate devices). Particularly, SIO210 may provide access to keyboard 103 and a mouse, or other peripheralinput devices such as keypads, biometric scanning devices, and voice oroptical recognition devices.

SIO 210 may also provide an interface for communications with one ormore sensor devices 212, which may include environment sensors, such asa temperature sensor or other cooling system sensors. These I/O devices,such as user input devices 211 and sensor devices 212, may interfacewith SIO 210 through wired or wireless connections.

Other resources may also be coupled to processor(s) 201 of IHS 100through chipset 202. For example, chipset 202 may be coupled to networkinterface 209, such as a Network Interface Controller (NIC). In certainembodiments, network interface 209 may be coupled to chipset 202 via aPCIe bus. Network interface 209 may support communication via variouswired and/or wireless networks.

Chipset 202 may also provide access to one or more hard disk and/orsolid state drives 215. In certain embodiments, chipset 202 may alsoprovide access to one or more optical drives 214 or otherremovable-media drives. Any or all of drive devices 214 and 215 may beintegral to IHS 100, or they may be located remotely. Chipset 202 mayalso provide access to one or more Universal Serial Bus (USB) ports 216.

In certain implementations, chipset IHS 202 may support an I²C(Inter-Integrated Circuit) bus that may be used to communicate withvarious types of microcontrollers, microprocessor and integratedcircuits that are typically integrated components of the motherboard ofthe IHS 100 and perform specialized operations. For example, such an I²Cbus may be utilized to transmit and receive keystroke and hoveringkeystroke information from an attached keyboard device, and to providethat information to an operating system (OS) executed by IHS 100.

Another resource that may be accessed by processor(s) 201 via chipset202 is Basic Input/Output System (BIOS) 217. Upon booting of IHS 100,processor(s) 201 may utilize BIOS 217 instructions to initialize andtest hardware components coupled to IHS 100 and to load an OS for use byIHS 100. BIOS 217 provides an abstraction layer that allows the OS tointerface with certain hardware components that are utilized by IHS 100.The Unified Extensible Firmware Interface (UEFI) was designed as asuccessor to BIOS; many modern IHSs utilize UEFI in addition to orinstead of a BIOS. As used herein, BIOS is also intended to encompassUEFI.

Chipset 202 may also provide an interface for communications with one ormore sensors 212. Sensors 212 may be disposed within display 101,chassis 102, keyboard 103, hinge 104, and/or trackpad 105, and mayinclude, but are not limited to: electric, magnetic, radio, optical,infrared, thermal, force, pressure, acoustic, ultrasonic, proximity,position, deformation, bending, direction, movement, velocity,gyroscope, rotation, and/or acceleration sensor(s).

In various embodiments, keyboard controller 300 (shown in FIG. 3) mayutilize different interfaces for communicating with the OS of IHS 100.For instance, keyboard controller 300 may interface with the chipset 202via super I/O controller 210.

FIG. 3 is a block diagram of electronic components of hovering keyboard103. As depicted, components of keyboard 103 include keyboard controlleror processor 300 coupled to electromechanical module 301, lightingmodule 302, and proximity module 303. Each of modules 301-303 mayinclude electronic circuits and/or program instructions that enable thatmodule to communicate with keyboard controller 300.

Electromechanical module 301 may be used to control the operation ofand/or to detect events originated by electromechanical layer 103A,lighting module 302 may be used to control the operation of backlightillumination layer 103B, and proximity module 303 may be used to controlthe operation of and/or to detect events originated by proximity sensinglayer 103C. In other implementations, an additional wirelesscommunication module (not shown) may be coupled to keyboard controller300 to enable communications between keyboard 103 and IHS 100 using asuitable wireless protocol.

Keyboard controller 300 may be configured to detect and identifyindividual physical keypresses or keystrokes made by the end user viaelectromechanical layer 103A. Keyboard controller or processor 300 mayalso be configured to control the operation of each individual LED ofbacklight illumination layer 103B using parameters such as, for example,a selected location (e.g., in an N×M matrix, as an identified key or setof keys, etc.), a selected color (e.g., when the backlight includes RGBLEDs), and a selected intensity (e.g., brighter or dimmer). In addition,keyboard controller 300 may be configured to detect and identifyindividual hovering keypresses made by the end user via proximitysensing layer 103C.

In various embodiments, IHS 100 and/or hovering keyboard 103 may notinclude all of components shown in FIGS. 2 and 3, respectively.Additionally, or alternatively, IHS 100 and/or hovering keyboard 103 mayinclude components in addition to those shown in FIGS. 2 and 3,respectively. Additionally, or alternatively, components represented asdiscrete in FIGS. 2 and 3 may instead be integrated with othercomponents. For example, all or a portion of the functionality providedby these various components may be provided as a System-On-Chip (SOC),or the like.

FIG. 4 is sectional view of hovering keyboard 103 in operation,according to some embodiments. As depicted, hovering keyboard 103includes electromechanical layer 103A, backlight illumination layer103B, and proximity sensing layer 103C. Electromechanical layer 103Ahosts a key assembly, which includes keycap 401 as well as a dome,switches, and/or levers configured to receive and capture physicalkeystrokes.

Backlight illumination layer 103B includes lighting element 402 underkey assembly 401. Illumination element 402 may include one or more LEDs(or one or more transparent areas from where light can exist a lightguide, for example) that are configured to shine light 405, using one ormore selected parameters (e.g., color, intensity, etc.), under keycap401. In some cases, element 402 may be disposed in a matrix of likeelements as part of backlight illumination layer 103B, each elementlocated under a corresponding key of electromechanical layer 103A.

Proximity sensing layer 103C includes proximity sensor 403 under keyassembly 401, such as a capacitive sensor, an infrared sensor, or anultrasonic sensor that is configured to provide sensing field 406.Examples of suitable proximity sensors include GESTIC sensors fromMicrochip Technology Inc. In some cases, proximity sensor 403 may bedisposed in a matrix of similar elements on proximity sensing layer103C, and each proximity sensor may be located under a respective key ofelectromechanical layer 103A.

In this example, assume that the user's finger or fingertip 404 isresting at position 407 relative to proximity sensing layer 103C. Whenfinger 404 travels by a selected or configurable distance 409 (in thevertical axis “z”) to position 408 from proximity sensing layer 103C,the disturbance caused by the user's finger 404 upon sense field 406triggers detection of a hovering keypress corresponding to keycap401—without finger 404 having to touch keycap 401.

In some cases, height 407 may be configured to become aligned with theheight of keycap 401, shown here as height 410. In that case, a hoveringkeypress can be detected when key cap 401 travels by distance 409 (e.g.,1 mm or 2 mm) from its initial position—a shorter travel distance (andless force) than a physical keypress would require.

In some implementations, the flickering or snapping action of afingertip by travel distance 409 may be interpreted as a hoveringkeystroke. An initial value (e.g., 2 mm) for travel distance 409 may beset during a calibration or training phase. Thereafter, in order todetect hovering keystrokes with reduced latency, processor 201 and/or300 may be configured to predict hovering keypresses based upon theuser's behavior.

FIGS. 5A and 5B show hovering keyboard 103 being used to detect handgestures according to some embodiments. Particularly, in configuration500A, a user's hand 500 hovers over keyboard 103 and performs asingle-handed gesture (e.g., a swiping gesture) in the positionindicated by light pattern 501. Different colors and/or brightnesssettings may be applied to light pattern 501 under selected keycaps, forexample, to guide a user's hand to a proper position.

For instance, selected key caps may light up with an intensityproportional to the distance between the hand and those keys, such thatthe amount of light increases (or the color changes) as the user moveshand 500 toward those keys. Then, the same lights (or all lights) mayblink a number of times when the user reaches the proper position fordetection, or when a gesture sequence is recognized. As a person ofordinary skill in the art will recognize, however, other suitablelighting patterns or instructions may be used.

Configuration 500B of FIG. 5B shows left hand 501L and right hand 501Rresting over hovering keyboard 103 above light patterns 503L and 503R,respectively. In this case, areas 503L and 503R indicate expected oridentified two-handed gestures (e.g., two concurrent swipes). Moreover,the IHS may light up selected keys 503L and 503R corresponding to theposition of hands 501L and 501R over hovering keyboard 103, such thateach of the selected keys is lit with a color and/or a brightnesscorresponding to a current distance between a portion of the hand abovethe selected keys and the hovering keyboard 103.

FIG. 6 is a flowchart of method 600 for configuring the layout of ahovering keyboard using gestures, according to some embodiments. Invarious implementations, program instructions for executing method 600may be stored in memory 205 and are executable by processor(s) 201. Insome cases, method 600 may be performed by one or more standalonesoftware applications, drivers, libraries, or toolkits, accessible viaan Application Programming Interface (API) or the like. Additionally, oralternatively, method 600 may be performed by the IHS's OS.

Method 600 begins at block 601. At block 602, method 600 beginsdetecting the user's hand(s) using proximity sensors 403 while the userperforms single handed or two-handed gestures, physical keystrokes, orhovering keystrokes. Generally, detection begins when proximity sensordata is received at IHS 100 from proximity sensing layer 103C ofhovering keyboard 103. In some implementations, proximity sensor datamay be processed, to some degree, by keyboard controller 300. Then, theproximity sensor data may be further processed by processor(s) 201.

For example, proximity signals that exhibit above-threshold distancesand/or motion over a suitable time interval are collected, and thenprocessor(s) 201 attempts to match the captured proximity sensor data toa geometric model of a user's hand. If a suitable match is found, thenthe hand may be recognized as that of the corresponding user.

In some embodiments, processor(s) 201 be configured to analyze proximitysignals from each distinct sensor in order to determine what part of theuser's hand each signal represents. A number of different hand-partassignment techniques may be used. For instance, each signal may beassigned a hand-part index. The hand-part index may include a discreteidentifier, confidence value, and/or hand-part probability distributionindicating the hand part or parts to which that signal is likely tocorrespond.

Machine learning may be used to assign each signal a hand-part indexand/or hand-part probability distribution. A machine-learning module mayanalyze a user's hand with reference to information learned from apreviously trained collection of known hands and/or hand features.

During a training phase, a variety of hand positions may be observed,and trainers may label various classifiers in the observed data. Theobserved data and annotations may then be used to generate one or moremachine-learned algorithms that map inputs (e.g., observation data fromproximity sensors) to desired outputs (e.g., hand-part indices forrelevant signals).

Thereafter, a partial virtual skeleton may be fit to at least one handpart identified. In some embodiments, a hand-part designation may beassigned to each skeletal segment and/or each joint. Such virtualskeleton may include any type and number of skeletal segments andjoints, including each individual finger.

In some embodiments, each joint may be assigned a number of parameters,such as, for example, Cartesian coordinates specifying its position,angles specifying its rotation, and other parameters (e.g., open hand,closed hand, length, width, joint position, angle of joint rotation, anda description of any finger segment). Then, a virtual skeleton may befit to each of a sequence of hand parts identified from the proximitysensor data.

At block 603, method 600 determines whether a gesture is being or hasbeen performed. For example, a “gesture” may have a Start phase (S) witha standalone gesture, a motion phase (M) with a sequence of gesturesfollowing each other, and an end phase (E) with another standalonegesture. In some embodiments, a look-up table may be used to store keyattributes and/or reference images of start, motion, and end phases foreach gesture sequence to be recognized, for two-handed and one-handedcases. As used herein, the term “look-up table” or “LUT” refers to anarray or matrix of data that contains items that are searched. In manycases, an LUT may be arranged as key-value pairs, where the keys are thedata items being searched (looked up) and the values are either theactual data or pointers to where the data are located.

The training phase may store user-specific finger/hand attributes (e.g.,asking user 101 to splay fingers), such as motion velocity orasynchrony. For example, a start or end phase LUT may be created toinclude reference images or attributes, whereas a motion phase LUT maybe created to include relative 6-axes data. The amount of time a userhas to hold their hands and/or fingers in position for each phase ofgesture sequence (S, M, and E) may be configurable.

In block 604, if a hand gesture is recognized, method 600 configures oneor more layout aspects of hovering keyboard 103, and method ends atblock 605. Otherwise, if the gesture is not recognized in block 603,control returns to block 602.

Examples of keyboard layout configuration operations include, but arenot limited to: enabling or disabling physical keypresses over selectedkeycaps or zones, enabling or disabling hovering keypresses overselected keycaps or zones, enabling or disabling gesture detection overselected keycaps or zones, enabling or disabling keyboard illuminationor lighting event under selected keycaps or zones, mapping keys toselected commands (e.g., according to the user's preferences, anapplication being executed, etc.).

FIG. 7 is a diagram of different zones of hovering keyboard 103. In someembodiments, hovering keyboard 103 includes number pad zone 701, “f-key”zone 702, right side 703, and left side 704. In other embodiments,however, any number of zones may be configured with any subset of keycaps as part of a layout configuration operation.

In various implementations, a user may configure any of zones 701-704 toperform gesture detection, physical keystroke detection, hoveringkeystroke detection, or any combination thereof. Additionally, oralternatively, each zone may be enabled or disabled to process selectedgestures, to the exclusion of other gestures. For example, zone 703 maybe configured to detect right swiping or waving gestures only, and zone704 may be configured to detect left swiping or waving gestures only.

For sake of illustration, consider an implementation example where rightside 703 of keyboard 103 is configured to map swiping gestures into afirst command (e.g. a right shift or arrow), and left side 704 isconfigured to map swiping gestures into a second command (e.g. a leftshift or arrow). In that manner, a user can control different aspects ofa slideshow application, for example, using hovering gestures, at thesame time as physical keystrokes (and/or hovering keystrokes) arereceived. The physical keystrokes may be mapped to the same application,or to any other application.

In some implementations, each of zones 701-704 may be selectivelyilluminated using backlight illumination layer 103B under respectivekeycaps to help a user visualize the different zones. For example, eachof zones 701-704 may light up with a different color in response to auser's command, or during execution of a zone configuration tool.

FIG. 8 is a diagram of a configuration example. In this example,physical keystrokes detected by hovering keyboard 103 may be mapped tofirst application 801. For example, first application 801 may be adocument processor or web browser.

Hovering keyboard 103 may also be split into two zones, left zone 803and right zone 804. In some cases, a swiping gesture detected on rightzone 804 may be translated into a next page or forward command in firstapplication 801, whereas a swiping gesture detected on left zone 803 maybe translated into a previous page or backward command in firstapplication 801.

In other cases, however, a swiping gesture detected on right zone 804may be translated into a next page or forward command 806 in secondapplication 802, and a swiping gesture detected on left zone 803 may betranslated into a previous page or backward command 805 in application802. For example, second application 802 may be a slideshow, andcommands 805 and 806 let the user navigate different media items 807.Meanwhile, hovering keyboard 103 may continue to map physical and/orhovering keystrokes to first application 801.

In some cases, a hovering keyboard 103 may have physical keystrokesmapped to a first application, hovering keystrokes mapped to a secondapplication, and hand gestures mapped to a third application. In somecases, one or more of these applications may be rendered in an externaldisplay coupled to IHS 100.

In other cases, hand gestures may themselves be used to configure layoutaspects of hovering keyboard 103. For instance, gestures may be used toenable or disable hovering keystroke detection in or more zones, toreconfigure or remap f-keys to custom commands, to enable or disablekeys, to change the keyboard layout, to set a keypress latencyadjustment, to set a hovering parameter or distance (407-410), to changea light pattern or to customize colors or light intensity, to togglebetween different operating modes of a foldable or 2-in-1 IHS (e.g., totoggle between keyboard and “surface” to write notes back and forth in adual display device), etc.

It should be understood that various operations described herein may beimplemented in software executed by logic or processing circuitry,hardware, or a combination thereof. The order in which each operation ofa given method is performed may be changed, and various operations maybe added, reordered, combined, omitted, modified, etc. It is intendedthat the invention(s) described herein embrace all such modificationsand changes and, accordingly, the above description should be regardedin an illustrative rather than a restrictive sense.

Although the invention(s) is/are described herein with reference tospecific embodiments, various modifications and changes can be madewithout departing from the scope of the present invention(s), as setforth in the claims below. Accordingly, the specification and figuresare to be regarded in an illustrative rather than a restrictive sense,and all such modifications are intended to be included within the scopeof the present invention(s). Any benefits, advantages, or solutions toproblems that are described herein with regard to specific embodimentsare not intended to be construed as a critical, required, or essentialfeature or element of any or all the claims.

Unless stated otherwise, terms such as “first” and “second” are used toarbitrarily distinguish between the elements such terms describe. Thus,these terms are not necessarily intended to indicate temporal or otherprioritization of such elements. The terms “coupled” or “operablycoupled” are defined as connected, although not necessarily directly,and not necessarily mechanically. The terms “a” and “an” are defined asone or more unless stated otherwise. The terms “comprise” (and any formof comprise, such as “comprises” and “comprising”), “have” (and any formof have, such as “has” and “having”), “include” (and any form ofinclude, such as “includes” and “including”) and “contain” (and any formof contain, such as “contains” and “containing”) are open-ended linkingverbs. As a result, a system, device, or apparatus that “comprises,”“has,” “includes” or “contains” one or more elements possesses those oneor more elements but is not limited to possessing only those one or moreelements. Similarly, a method or process that “comprises,” “has,”“includes” or “contains” one or more operations possesses those one ormore operations but is not limited to possessing only those one or moreoperations.

1. An Information Handling System (IHS), comprising: a processor; and amemory coupled to the processor, the memory having program instructionsstored thereon that, upon execution by the processor, cause the IHS to:detect a hand gesture using proximity sensors disposed on a keyboardcoupled to the IHS, at least in part, by fitting proximity data obtainedby the proximity sensors to a partial virtual skeleton of the handhaving one or more parameters selected from the group consisting of: alength, a width, a joint position, an angle of joint rotation, and afinger segment; and configure a layout of the keyboard based on thedetection.
 2. (canceled)
 3. (canceled)
 4. The IHS of claim 1, whereinthe hand gesture comprises a swipe.
 5. The IHS of claim 1, wherein toconfigure the layout, the program instructions, upon execution, furthercause the IHS to map a key selected by a user to a correspondingcommand.
 6. The IHS of claim 1, wherein to configure the layout, theprogram instructions, upon execution, further cause the IHS to detecthovering keystrokes to the exclusion of physical keystrokes.
 7. The IHSof claim 1, wherein to configure the layout, the program instructions,upon execution, further cause the IHS to detect physical keystrokes tothe exclusion of hovering keystrokes.
 8. The IHS of claim 1, wherein toconfigure the layout, the program instructions, upon execution, furthercause the IHS to detect physical keystrokes and hovering keystrokesconcurrently.
 9. The IHS of claim 1, wherein to configure the layout,the program instructions, upon execution, further cause the IHS to map afirst hovering keystroke over a first keycap to a first applicationexecuted by the IHS, and to map a second hovering keystroke over asecond keycap to a second application executed by the IHS.
 10. The IHSof claim 9, wherein the first application is rendered on a displayintegrated into the IHS, and wherein the second application is renderedon an external display.
 11. The IHS of claim 1, wherein to configure thelayout, the program instructions, upon execution, further cause the IHSto map a hovering keystroke over a given keycap to a first applicationexecuted by the IHS, and to map a physical keystroke of the given keycapto a second application executed by the IHS.
 12. The IHS of claim 1,wherein to configure the layout, the program instructions, uponexecution, further cause the IHS to enable hovering keystrokes over afirst subset of keycaps and disable hovering keystrokes over a secondsubset of keycaps.
 13. The IHS of claim 1, wherein to configure thelayout, the program instructions, upon execution, further cause the IHSto enable or disable a lighting effect provided via a backlightillumination layer of the keyboard.
 14. A method, comprising: detectinga hand gesture using proximity sensors disposed on a keyboard coupled toan Information Handling System (IHS), at least in part, by fittingproximity data obtained by the proximity sensors to a partial virtualskeleton of the hand having one or more parameters selected from thegroup consisting of: a length, a width, a joint position, an angle ofjoint rotation, and a finger segment; and configuring a layout of thekeyboard based on the detection.
 15. (canceled)
 16. The method of claim14, wherein configuring the layout further comprises configuring thekeyboard to detect one of: (i) hovering keystrokes only, (ii) physicalkeystrokes only, or (iii) physical keystrokes and hovering keystrokesconcurrently.
 17. The method of claim 14, wherein configuring the layoutfurther comprises mapping a hovering keystroke over a given keycap to afirst application executed by the IHS and mapping a physical keystrokeof the given keycap to a second application executed by the IHS.
 18. Themethod of claim 14, wherein configuring the layout comprises enablinghovering keystrokes over a first a subset of keycaps and disablinghovering keystrokes over a second subset of keycaps.
 19. The method ofclaim 14, wherein configuring the layout comprises selecting a color oran intensity of a light provided by a backlight illumination layer ofthe keyboard.
 20. A hardware memory device having program instructionsstored thereon that, upon execution by a processor of an InformationHandling System (IHS), cause the IHS to: detect a hand gesture usingproximity sensors disposed on a keyboard coupled to the IHS, at least inpart, by fitting proximity data obtained by the proximity sensors to apartial virtual skeleton of the hand having one or more parametersselected from the group consisting of: a length, a width, a jointposition, an angle of joint rotation, and a finger segment; andconfigure a layout of the keyboard based on the detection.